← previous blocknext block →recent activity
Analyzing
Block #84,361,335
56 transactions · 40 stateful · 2026-06-29 01:01:15 UTC
Parallelism
82/100
Blocked
65%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,361,335 · 56 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
1w02w13w04w15w16w28w310w412w513w614w015w145w346w647w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x7dc64b2c…05e7
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity