← previous blocknext block →recent activity
Analyzing
Block #75,471,077
14 transactions · 11 stateful · 2026-05-18 20:35:34 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,471,077 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x12bc0d2c…1c12
0x34b655…2a6f
4 touches
1 conflict
0x37cfaf01…4a46
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x75f6889e…7f1e
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity