← previous blocknext block →recent activity
Analyzing
Block #80,164,213
24 transactions · 17 stateful · 2026-06-09 14:23:21 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,164,213 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w16w07w19w217w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0x9edc0a7d…2724
0x34b655…2a6f
6 touches
3 conflicts
0x754c7f04…5673
0x34b655…2a6f
6 touches
3 conflicts
0x87210308…d018
0x34b655…2a6f
6 touches
3 conflicts
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0x65bb8d8c…8bb0
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
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