← previous blocknext block →recent activity
Analyzing
Block #86,811,347
16 transactions · 11 stateful · 2026-07-10 09:26:29 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,811,347 · 16 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
3w04w05w16w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b2f849…41a9
0x34b655…2a6f
4 touches
1 conflict
0x7044735f…ecc4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0x08cc68a2c8…482a59
Audit this contract →
← previous block·next block →recent activity