← previous blocknext block →recent activity
Analyzing
Block #80,589,016
16 transactions · 16 stateful · 2026-06-11 13:35:44 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,589,016 · 16 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
1w02w13w14w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a3
0xb327fb…6b13
6 touches
3 conflicts
0x8a35acfb…d1a2
0xb327fb…6b13
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1e451306…7993
0xb327fb…6b13
4 touches
1 conflict
0x50e10826…843b
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d19e
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: Perpl
3 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity