← previous blocknext block →recent activity
Analyzing
Block #86,927,044
10 transactions · 8 stateful · 2026-07-10 22:20:11 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,927,044 · 10 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
1w02w13w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fa1ba4f…a56f
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a570
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x7f2141d6…42bd
0x34b655…2a6f
4 touches
1 conflict
0xfb46bac1…645f
0x34b655…2a6f
3 touches
1 conflict
0x2d8af94a…722c
0x34b655…2a6f
2 touches
0 conflicts
0x402bdfc2…98c9
0x34b655…2a6f
2 touches
0 conflicts
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 0x8fa1ba4f68…24a56f
Audit this contract →
← previous block·next block →recent activity