← previous blocknext block →recent activity
Analyzing
Block #80,265,332
22 transactions · 14 stateful · 2026-06-10 01:37:44 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,265,332 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w117w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x88c56519…b0e8
0x34b655…2a6f
6 touches
3 conflicts
0x096c7f83…68af
0x34b655…2a6f
4 touches
1 conflict
0x0ac67576…1cc5
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x12c6929d…e7db
0x34b655…2a6f
4 touches
1 conflict
0x16452d34…7c10
0x34b655…2a6f
4 touches
1 conflict
0x25aa11ec…c8f4
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity