← previous blocknext block →recent activity
Analyzing
Block #86,511,634
17 transactions · 14 stateful · 2026-07-09 00:01:18 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,511,634 · 17 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
6w07w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xe1d1f14d…3ffb
0x34b655…2a6f
4 touches
1 conflict
0x5ccbdfb6…3e06
0x34b655…2a6f
4 touches
1 conflict
0x211d520a…bf67
0x34b655…2a6f
2 touches
0 conflicts
0x356516c5…3792
0x34b655…2a6f
2 touches
0 conflicts
0x3a37aad1…720f
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 0x5e782d178d…db5317
Audit this contract →
← previous block·next block →recent activity