← previous blocknext block →recent activity
Analyzing
Block #84,361,229
21 transactions · 18 stateful · 2026-06-29 01:00:32 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,361,229 · 21 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
1w02w13w24w07w18w09w112w013w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd01910c9…9418
0x34b655…2a6f
6 touches
3 conflicts
0xc4a7a4bb…3134
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0x32229dd3…4dbb
0x34b655…2a6f
6 touches
3 conflicts
0x3ec82b22…1f46
0x34b655…2a6f
6 touches
3 conflicts
0x3f4dc602…5a18
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity