← previous blocknext block →recent activity
Analyzing
Block #86,689,524
17 transactions · 13 stateful · 2026-07-09 19:52:53 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,689,524 · 17 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
1w02w17w013w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xfe2b47…c052
4 touches
1 conflict
0x0f06ca04…e783
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0f1215c9…20d5
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xbaa199db…50fd
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
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 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity