← previous blocknext block →recent activity
Analyzing
Block #87,624,684
35 transactions · 31 stateful · 2026-07-14 04:05:32 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.66
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,624,684 · 35 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w010w112w113w214w315w416w517w618w719w820w921w1022w1125w326w427w528w633w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x08330b36…ae29
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x13510de3…1c68
0x34b655…2a6f
10 touches
10 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x91d48be7…e4e8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity