← previous blocknext block →recent activity
Analyzing
Block #87,748,831
21 transactions · 17 stateful · 2026-07-14 17:55:57 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,748,831 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w412w313w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
12 touches
15 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x4755fafb…859b
0x34b655…2a6f
10 touches
10 conflicts
0xfa6e44cf…eda0
0x34b655…2a6f
10 touches
10 conflicts
0x58620f29…db5a
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x9b309173…f9c0
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity