← previous blocknext block →recent activity
Analyzing
Block #86,990,163
15 transactions · 14 stateful · 2026-07-11 05:21:53 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,990,163 · 15 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
4w05w16w07w19w010w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x072c4867…c7a9
0x34b655…2a6f
4 touches
1 conflict
0x26918bca…6c75
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x3c6f6172…5d96
0x34b655…2a6f
4 touches
1 conflict
0x426e1f22…5ff9
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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
1 conflict on slot 0x06aed19eee…1cca57
Audit this contract →
← previous block·next block →recent activity