← previous blocknext block →recent activity
Analyzing
Block #86,675,427
20 transactions · 17 stateful · 2026-07-09 18:18:48 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,675,427 · 20 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
1w02w14w05w07w18w29w010w113w114w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1647db7…f853
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x1683ba92…41ac
0x34b655…2a6f
4 touches
1 conflict
0x27c61162…b3a9
0x34b655…2a6f
4 touches
1 conflict
0x2fa2e180…87a9
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x4572c9a0…5cf9
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 0xc1647db712…42f853
Audit this contract →
← previous block·next block →recent activity