← previous blocknext block →recent activity
Analyzing
Block #87,262,927
41 transactions · 35 stateful · 2026-07-12 11:45:33 UTC
Parallelism
61/100
Blocked
80%
Avg conflicts / tx
3.66
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,262,927 · 41 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w411w012w113w214w315w416w517w625w528w529w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
22 touches
55 conflicts
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x5f72d58f…c445
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 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 0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block·next block →recent activity