← previous blocknext block →recent activity
Analyzing
Block #86,617,765
34 transactions · 20 stateful · 2026-07-09 11:52:23 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,617,765 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w012w114w117w018w119w221w224w326w327w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x53dfdb29…1ee0
0x065c9d…c394
5 touches
3 conflicts
0x1299b030…e115
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
4 touches
1 conflict
0x9068a9bc…86ee
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity