← previous blocknext block →recent activity
Analyzing
Block #86,103,824
34 transactions · 26 stateful · 2026-07-07 02:37:33 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,103,824 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w010w112w013w114w219w024w325w430w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd1b162…bee6
0x34b655…2a6f
10 touches
10 conflicts
0x9868ee17…0695
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfcb5fe79…c20a
0x34b655…2a6f
6 touches
3 conflicts
0x931619e4…3b17
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x4303b2b8…f061
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 0xacd1b16256…3bbee6
Audit this contract →
← previous block·next block →recent activity