← previous blocknext block →recent activity
Analyzing
Block #84,352,479
22 transactions · 18 stateful · 2026-06-29 00:02:08 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,352,479 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w28w09w111w212w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3d4ec808…d43b
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0x1f9d7063…6b89
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…4735
0x1b6862…e19c
4 touches
1 conflict
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity