← previous blocknext block →recent activity
Analyzing
Block #74,516,126
22 transactions · 13 stateful · 2026-05-14 10:12:44 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,516,126 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w07w19w210w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0xd0a301b4…5336
0x065c9d…c394
3 touches
1 conflict
0xd121d3c5…f0b7
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity