← previous blocknext block →recent activity
Analyzing
Block #76,117,564
12 transactions · 11 stateful · 2026-05-21 20:33:24 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,117,564 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0x67cfc02c…9f9a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x84fb2a36…db89
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0xa17ec269…7cdd
0x1d1325…2305
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: Perpl
3 conflicts on slot 0xb138d08737…2b4689
Audit this contract →
← previous block·next block →recent activity