← previous blocknext block →recent activity
Analyzing
Block #86,827,886
22 transactions · 20 stateful · 2026-07-10 11:17:15 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,827,886 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w09w011w012w214w115w216w117w318w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xcf736cb7…1752
0x40c49f…2af0
5 touches
3 conflicts
0x053d5b4c…25de
0x40c49f…2af0
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0x40c49f17…d22af0
6 conflicts on slot 0x76d1e78d12…117877
Audit this contract →
← previous block·next block →recent activity