← previous blocknext block →recent activity
Analyzing
Block #76,263,488
14 transactions · 11 stateful · 2026-05-22 12:45:04 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,263,488 · 14 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
1w02w03w15w06w17w09w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d34b099…ff86
0x34b655…2a6f
6 touches
3 conflicts
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf9b8ae99…32b3
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 0x9d34b099b8…42ff86
Audit this contract →
← previous block·next block →recent activity