← previous blocknext block →recent activity
Analyzing
Block #84,500,857
19 transactions · 15 stateful · 2026-06-29 16:31:25 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,500,857 · 19 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
2w03w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xa7d01c27…dc15
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x8e739938…e7ab
0x34b655…2a6f
4 touches
1 conflict
0xcbecfb96…3e12
0x405b63…7777
2 touches
1 conflict
0xbcc1b459…f94f
0x3bd359…433a
2 touches
0 conflicts
0x9aa23381…e172
0x405b63…7777
2 touches
0 conflicts
0xa74cd79c…705a
0x405b63…7777
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity