← previous blocknext block →recent activity
Analyzing
Block #76,262,967
10 transactions · 8 stateful · 2026-05-22 12:41:40 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,262,967 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d34b099…ff86
0x34b655…2a6f
4 touches
1 conflict
0x1a00e894…ef5d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x7e3d750f…04fd
0x34b655…2a6f
2 touches
0 conflicts
0x81ea9d30…fbe1
0x34b655…2a6f
2 touches
0 conflicts
0x9e5ff28e…6507
0x34b655…2a6f
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 0x9d34b099b8…42ff86
Audit this contract →
← previous block·next block →recent activity