← previous blocknext block →recent activity
Analyzing
Block #76,559,572
20 transactions · 16 stateful · 2026-05-23 21:36:46 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,559,572 · 20 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
2w03w06w111w212w016w317w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf282c2b3…28b4
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x11a2bada…01bf
0x34b655…2a6f
4 touches
1 conflict
0x12e7c471…901c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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: 0xa6afd386…b0d132
3 conflicts on slot 0xf282c2b36a…3228b4
Audit this contract →
← previous block·next block →recent activity