← previous blocknext block →recent activity
Analyzing
Block #86,513,322
9 transactions · 7 stateful · 2026-07-09 00:12:35 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,513,322 · 9 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
3w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1d1f14d…3ffb
0x34b655…2a6f
4 touches
1 conflict
0x5f34fd08…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x7c6a17fa…e95d
0x34b655…2a6f
4 touches
1 conflict
0x57bb625a…286d
0x34b655…2a6f
4 touches
1 conflict
0x08552893…1c28
0x34b655…2a6f
2 touches
0 conflicts
0x0e53397f…faa1
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
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 0xe1d1f14d10…743ffb
Audit this contract →
← previous block·next block →recent activity