← previous blocknext block →recent activity
Analyzing
Block #86,300,423
13 transactions · 11 stateful · 2026-07-08 00:30:07 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,300,423 · 13 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5012b17…2996
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xb0636967…a8e1
0x34b655…2a6f
4 touches
1 conflict
0xb625be5c…7e21
0x34b655…2a6f
4 touches
1 conflict
0xc7f7d98f…cfe7
0x34b655…2a6f
4 touches
1 conflict
0xcd90ec4b…d8d3
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 0xf5012b1716…392996
Audit this contract →
← previous block·next block →recent activity