← previous blocknext block →recent activity
Analyzing
Block #84,352,238
29 transactions · 24 stateful · 2026-06-29 00:00:31 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,352,238 · 29 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
1w02w13w26w39w310w211w012w113w014w115w216w319w021w423w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x454d8940…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0x79af19df…6a67
0xd32edf…ff58
7 touches
6 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0x3d4ec808…d43b
0x34b655…2a6f
6 touches
3 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
6 touches
3 conflicts
0xd33e70b0…1515
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity