← previous blocknext block →recent activity
Analyzing
Block #74,333,107
19 transactions · 17 stateful · 2026-05-13 13:53:32 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,333,107 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w613w014w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0xd6aabe89…92f5
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0x19b70cb3…9891
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
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: 0xab35264b…1cfa38
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity