← previous blocknext block →recent activity
Analyzing
Block #87,497,022
37 transactions · 29 stateful · 2026-07-13 13:50:57 UTC
Parallelism
65/100
Blocked
69%
Avg conflicts / tx
1.57
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,497,022 · 37 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w09w110w011w113w218w119w220w321w422w525w629w730w234w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
10 touches
10 conflicts
0x092832cd…7b28
0x34b655…2a6f
10 touches
10 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xcfb1c19c…af5b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity