← previous blocknext block →recent activity
Analyzing
Block #84,352,288
11 transactions · 9 stateful · 2026-06-29 00:00:51 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,352,288 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xfc8b4565…aa86
0x34b655…2a6f
4 touches
1 conflict
0xffb1ee54…7c2c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…a0ab
0x16f70c…c3dd
2 touches
0 conflicts
0x0c366266…77e1
0x34b655…2a6f
2 touches
0 conflicts
0x16e06a6b…4395
0x34b655…2a6f
2 touches
0 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity