← previous blocknext block →recent activity
Analyzing
Block #86,338,220
16 transactions · 14 stateful · 2026-07-08 04:42:41 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,338,220 · 16 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
1w03w04w110w111w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503b3a72…f6df
0x34b655…2a6f
4 touches
1 conflict
0x94939031…f6ea
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x112cf8ad…6e4f
0xa6afd3…d132
4 touches
1 conflict
0x3181bd2d…cf15
0xa6afd3…d132
4 touches
1 conflict
0xec0e0220…cb90
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
1 conflict on slot 0x503b3a72dc…c4f6df
Audit this contract →
← previous block·next block →recent activity