← previous blocknext block →recent activity

Analyzing

Block #73,476,084

16 transactions · 13 stateful · 2026-05-09 14:32:13 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,476,084  ·  16 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

0x00000000…0003

0x116e7d…d8f1

6 touches
3 conflicts

0xb7143610…adc4

0x3bd359…433a

6 touches
3 conflicts

0x692a4122…76b8

0x350035…7777

6 touches
3 conflicts

0x00000000…0000

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0002

0x116e7d…d8f1

6 touches
3 conflicts

0x83cde744…b76b

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

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: 0x116e7d07…d7d8f1

3 conflicts on slot 0x0000000000…000003

← previous block·next block →recent activity