← previous blocknext block →recent activity
Analyzing
Block #84,458,103
31 transactions · 27 stateful · 2026-06-29 11:46:07 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
2.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,458,103 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w38w211w012w113w214w315w416w522w424w425w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xc05b880b…7746
0xa6afd3…d132
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0x35de07e6…7751
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x826cce18…251c
0x34b655…2a6f
10 touches
10 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity