← previous blocknext block →recent activity
Analyzing
Block #80,630,806
18 transactions · 14 stateful · 2026-06-11 18:14:53 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,630,806 · 18 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
1w02w13w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2263bea…6a9f
0x69df8a…6292
4 touches
1 conflict
0xea8e47b0…abfe
0x69df8a…6292
4 touches
1 conflict
0xed7dd7db…6022
0x69df8a…6292
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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: 0x69df8a43…506292
1 conflict on slot 0xe2263beaa4…316a9f
Audit this contract →
← previous block·next block →recent activity