← previous blocknext block →recent activity
Analyzing
Block #84,363,094
27 transactions · 24 stateful · 2026-06-29 01:12:58 UTC
Parallelism
78/100
Blocked
63%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,363,094 · 27 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
1w02w13w24w36w07w18w29w310w011w114w015w116w217w318w422w423w224w526w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3ec82b22…1f46
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
6 touches
3 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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity