← previous blocknext block →recent activity
Analyzing
Block #84,135,299
15 transactions · 13 stateful · 2026-06-27 23:55:30 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,135,299 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0592331…1e7f
0x34b655…2a6f
8 touches
6 conflicts
0x5ba4db2b…2f04
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0xd7e72076…294a
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x0da9ce78…aee3
0x34b655…2a6f
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 0xa059233109…d51e7f
Audit this contract →
← previous block·next block →recent activity