← previous blocknext block →recent activity
Analyzing
Block #84,335,959
22 transactions · 21 stateful · 2026-06-28 22:12:00 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,335,959 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w110w211w013w116w417w419w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dc64b2c…05e7
0x34b655…2a6f
8 touches
6 conflicts
0x8fb0fecf…cb2f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x76ae59bb…ec93
0xd32edf…ff58
5 touches
3 conflicts
0x1da7723c…80a8
0x1b6862…e19c
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
6 conflicts on slot 0x7dc64b2c34…6405e7
Audit this contract →
← previous block·next block →recent activity