← previous blocknext block →recent activity
Analyzing
Block #87,716,948
37 transactions · 32 stateful · 2026-07-14 14:22:41 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.08
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,716,948 · 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
1w03w04w15w06w07w08w113w016w117w218w319w423w526w127w728w829w231w133w936w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7525206c…fbd5
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x76ebf9c2…e0ef
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