← previous blocknext block →recent activity
Analyzing
Block #86,513,803
18 transactions · 15 stateful · 2026-07-09 00:15:48 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,513,803 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w29w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0x8631c06c…1922
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa55cdf2a…1c64
0x34b655…2a6f
6 touches
3 conflicts
0xb6aedce9…a483
0x34b655…2a6f
6 touches
3 conflicts
0xdf6fce37…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
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 0x9a291a5639…d39a9c
Audit this contract →
← previous block·next block →recent activity