← previous blocknext block →recent activity
Analyzing
Block #86,706,907
10 transactions · 9 stateful · 2026-07-09 21:48:49 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,706,907 · 10 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
2w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b9e5ecc…2bc7
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
0x34b655…2a6f
4 touches
1 conflict
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x93701943…012b
0x34b655…2a6f
4 touches
1 conflict
0x93c3b3b3…faf9
0x34b655…2a6f
4 touches
1 conflict
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x22d41e3b…3336
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
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 0x5b9e5ecc6a…8e2bc7
Audit this contract →
← previous block·next block →recent activity