← previous blocknext block →recent activity

Analyzing

Block #73,029,523

10 transactions · 9 stateful · 2026-05-07 13:01:00 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,029,523  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0x63a04522…f10d

0x065c9d…c394

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x934f816e…f96b

0xa6afd3…d132

3 touches
1 conflict

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x1e349dde…a33a

0x754704…b603

2 touches
0 conflicts

0x00000000…0000

0xb02793…e402

2 touches
0 conflicts

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: 0x754704bc…afb603

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity