← previous blocknext block →recent activity
Analyzing
Block #80,224,125
17 transactions · 8 stateful · 2026-06-09 21:02:53 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,224,125 · 17 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
1w02w14w05w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0xbeda8507…4e81
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x259dfd61…c34a
0x34b655…2a6f
2 touches
0 conflicts
0x2c616c82…0772
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity