← previous blocknext block →recent activity
Analyzing
Block #86,847,777
69 transactions · 56 stateful · 2026-07-10 13:30:09 UTC
Parallelism
65/100
Blocked
73%
Avg conflicts / tx
4.09
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #86,847,777 · 69 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w29w310w411w512w613w714w850w953w955w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…00c9
0x34b655…2a6f
18 touches
36 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
14 touches
21 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 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
136 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity