← previous blocknext block →recent activity
Analyzing
Block #74,460,367
30 transactions · 19 stateful · 2026-05-14 04:00:32 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,460,367 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w69w715w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x37d49489…9309
0x34b655…2a6f
6 touches
3 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
6 touches
3 conflicts
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x9dc9fa5f…7f23
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
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: 0xab35264b…1cfa38
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity