← previous blocknext block →recent activity
Analyzing
Block #80,341,398
14 transactions · 10 stateful · 2026-06-10 10:04:49 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,341,398 · 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
4w05w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc009105d…96f7
0xb327fb…6b13
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0xb327fb…6b13
4 touches
1 conflict
0x50e10826…843b
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d19d
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d19e
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a2
0xb327fb…6b13
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: 0xb327fb26…e56b13
1 conflict on slot 0xc009105db3…e996f7
Audit this contract →
← previous block·next block →recent activity