← previous blocknext block →recent activity
Analyzing
Block #86,698,866
17 transactions · 14 stateful · 2026-07-09 20:55:10 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,698,866 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w29w310w211w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x68d1ca28…6962
0x34b655…2a6f
4 touches
1 conflict
0x6997833d…b1c5
0x34b655…2a6f
4 touches
1 conflict
0xc5a6bdfc…3abc
0x34b655…2a6f
4 touches
1 conflict
0xcc3f7ee8…7924
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda3eb3c3…9d60
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
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity