← previous blocknext block →recent activity
Analyzing
Block #80,328,589
21 transactions · 17 stateful · 2026-06-10 08:39:28 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,328,589 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w116w018w219w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb138d087…4689
0x34b655…2a6f
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9a54f439…de63
0x34b655…2a6f
6 touches
3 conflicts
0x656875af…444b
0xc8689a…ee79
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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
6 conflicts on slot 0xb138d08737…2b4689
Audit this contract →
← previous block·next block →recent activity