← previous blocknext block →recent activity
Analyzing
Block #86,539,959
26 transactions · 20 stateful · 2026-07-09 03:10:37 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,539,959 · 26 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
2w012w014w115w117w023w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc4ed41b1…6db5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa1865516…fa1e
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd89f212d…2bbf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity