← previous blocknext block →recent activity

Analyzing

Block #70,955,893

15 transactions · 14 stateful · 2026-04-27 22:39:02 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,955,893  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x8d0b2e09…dedc

0x065c9d…c394

6 touches
3 conflicts

0x71083f9f…877b

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x131a2e…0da9

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0x8fd63a…536c

4 touches
1 conflict

0x00000000…0001

0x8fd63a…536c

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x065c9d28…a9c394

3 conflicts on slot 0x8d0b2e09e4…28dedc

← previous block·next block →recent activity