← previous blocknext block →recent activity
Analyzing
Block #80,165,219
24 transactions · 17 stateful · 2026-06-09 14:30:04 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,165,219 · 24 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
1w02w13w26w07w09w313w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7f6893b…7d2f
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
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
3 conflicts on slot 0xf7f6893b2e…477d2f
Audit this contract →
← previous block·next block →recent activity