← previous blocknext block →recent activity
Analyzing
Block #86,703,715
18 transactions · 17 stateful · 2026-07-09 21:27:33 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,703,715 · 18 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
1w06w07w18w113w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde30d77…b032
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x14b7032b…f4f6
0x34b655…2a6f
4 touches
1 conflict
0x2148526a…af7b
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3b
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
3 conflicts on slot 0xbde30d77ef…1cb032
Audit this contract →
← previous block·next block →recent activity