← previous blocknext block →recent activity
Analyzing
Block #74,332,936
34 transactions · 25 stateful · 2026-05-13 13:52:25 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,332,936 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w113w214w315w416w527w228w231w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x32adb28c…b96c
0xd32edf…ff58
5 touches
3 conflicts
0x874f5c70…608f
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xcc692f30…a188
0x065c9d…c394
4 touches
1 conflict
0xdb9a00cd…ff71
0x065c9d…c394
3 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
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity