← previous blocknext block →recent activity
Analyzing
Block #85,989,964
27 transactions · 21 stateful · 2026-07-06 13:57:29 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,989,964 · 27 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
2w04w16w07w08w114w221w022w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xff9db98c…02f8
0x065c9d…c394
5 touches
3 conflicts
0xda42e57d…12d0
0x065c9d…c394
4 touches
1 conflict
0x002dfab7…aa48
0x34b655…2a6f
4 touches
1 conflict
0x15eb57da…1fc8
0x34b655…2a6f
4 touches
1 conflict
0x1b159f3d…9163
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity