← previous blocknext block →recent activity
Analyzing
Block #86,058,246
14 transactions · 13 stateful · 2026-07-06 21:33:32 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,058,246 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93f33c97…2848
0x34b655…2a6f
4 touches
1 conflict
0x93f33c97…2849
0x34b655…2a6f
4 touches
1 conflict
0xb274cb13…808b
0x34b655…2a6f
4 touches
1 conflict
0xe815ba2a…f9cf
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x93f33c9799…172848
Audit this contract →
← previous block·next block →recent activity