← previous blocknext block →recent activity
Analyzing
Block #87,713,606
63 transactions · 57 stateful · 2026-07-14 14:00:10 UTC
Parallelism
67/100
Blocked
74%
Avg conflicts / tx
2.97
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,713,606 · 63 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w26w37w48w09w110w211w013w114w215w340w241w443w353w554w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
22 touches
55 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
22 touches
55 conflicts
0x92385428…6941
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0001
0xc1ff9f…b0fc
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x820b2f6b…9263
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc3a8e1d6…e816
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
55 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity