← previous blocknext block →recent activity
Analyzing
Block #82,970,309
26 transactions · 21 stateful · 2026-06-22 14:18:45 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,970,309 · 26 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
1w03w05w06w110w113w115w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588da1c1…6ae5
0x34b655…2a6f
6 touches
3 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x2b51c05e…197d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2760bd9e…44c1
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
3 conflicts on slot 0x588da1c18d…a86ae5
Audit this contract →
← previous block·next block →recent activity