← previous blocknext block →recent activity
Analyzing
Block #86,983,136
19 transactions · 17 stateful · 2026-07-11 04:34:55 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,983,136 · 19 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
1w02w13w04w15w26w37w48w59w612w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xf5d6bb67…5649
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0x75959b84…9bda
0x34b655…2a6f
10 touches
10 conflicts
0x75cabd81…3f49
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity