← previous blocknext block →recent activity
Analyzing
Block #80,340,913
19 transactions · 17 stateful · 2026-06-10 10:01:35 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,340,913 · 19 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
1w02w16w07w18w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a3
0xb327fb…6b13
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a2
0xb327fb…6b13
6 touches
3 conflicts
0xc009105d…96f7
0xb327fb…6b13
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
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
3 conflicts on slot 0x8a35acfbc1…6bd1a3
Audit this contract →
← previous block·next block →recent activity