← previous blocknext block →recent activity
Analyzing
Block #76,113,843
12 transactions · 10 stateful · 2026-05-21 20:08:37 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,113,843 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xcda9bc1f…69dc
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x5b378780…92d8
0xd32edf…ff58
3 touches
1 conflict
0x2ff6ee39…dc92
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x5dece9e1…b7a9
0x065c9d…c394
2 touches
0 conflicts
0xd70c736d…e269
0x065c9d…c394
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
1 conflict on slot 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity