← previous blocknext block →recent activity
Analyzing
Block #80,826,332
21 transactions · 13 stateful · 2026-06-12 15:58:32 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,826,332 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e5d7a21…b2fe
0x34b655…2a6f
3 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x485d6a0e…963a
0x065c9d…c394
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2425f622…ad33
0x34b655…2a6f
2 touches
0 conflicts
0x30c870a0…c02d
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
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 0x6e5d7a21e3…3bb2fe
Audit this contract →
← previous block·next block →recent activity