← previous blocknext block →recent activity
Analyzing
Block #80,296,206
13 transactions · 12 stateful · 2026-06-10 05:03:28 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,296,206 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x143dba04…1b98
0xb327fb…6b13
4 touches
1 conflict
0x1e451306…7993
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a2
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a3
0xb327fb…6b13
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xa0749d24…af44
0x065c9d…c394
2 touches
0 conflicts
0xeece21b9…1fa2
0x065c9d…c394
2 touches
0 conflicts
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 0x143dba04c2…a61b98
Audit this contract →
← previous block·next block →recent activity