← previous blocknext block →recent activity
Analyzing
Block #86,499,154
26 transactions · 20 stateful · 2026-07-08 22:38:07 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,499,154 · 26 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
1w04w05w16w210w011w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x80f1cdc2…4bde
0x34b655…2a6f
4 touches
1 conflict
0xa7e45018…b59c
0x34b655…2a6f
4 touches
1 conflict
0xd4541380…f8d2
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity