← previous blocknext block →recent activity
Analyzing
Block #86,365,058
16 transactions · 15 stateful · 2026-07-08 07:41:43 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,365,058 · 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
10w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96f9d32e…9ddf
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1613b04a…914e
0x34b655…2a6f
2 touches
0 conflicts
0x459573ed…fbbe
0x34b655…2a6f
2 touches
0 conflicts
0x503b3a72…f6df
0x34b655…2a6f
2 touches
0 conflicts
0x7b3a71df…68d7
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 0x96f9d32ede…8b9ddf
Audit this contract →
← previous block·next block →recent activity