← previous blocknext block →recent activity
Analyzing
Block #84,355,432
24 transactions · 21 stateful · 2026-06-29 00:21:50 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,355,432 · 24 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
6w07w110w111w212w014w120w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf9957df…8d42
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x37a276a3…673f
0x34b655…2a6f
4 touches
1 conflict
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
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
3 conflicts on slot 0xdf9957df13…738d42
Audit this contract →
← previous block·next block →recent activity