← previous blocknext block →recent activity
Analyzing
Block #80,678,873
15 transactions · 11 stateful · 2026-06-11 23:35:16 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,678,873 · 15 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
2w08w09w111w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d1bb389…c7d9
0xb327fb…6b13
4 touches
1 conflict
0xfe1362cf…bb85
0xa6afd3…d132
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…d1a0
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a1
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 0x9d1bb3891b…cac7d9
Audit this contract →
← previous block·next block →recent activity