← previous blocknext block →recent activity
Analyzing
Block #80,296,262
14 transactions · 13 stateful · 2026-06-10 05:03:50 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,296,262 · 14 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
1w02w04w15w06w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d1bb389…c7d9
0xb327fb…6b13
4 touches
1 conflict
0x0335ae80…8414
0xb327fb…6b13
4 touches
1 conflict
0x143dba04…1b98
0xb327fb…6b13
4 touches
1 conflict
0x1e451306…7993
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
0x8a35acfb…d1a3
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 0x9d1bb3891b…cac7d9
Audit this contract →
← previous block·next block →recent activity