← previous blocknext block →recent activity
Analyzing
Block #87,759,087
19 transactions · 18 stateful · 2026-07-14 19:04:31 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,759,087 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0xf3d10975…0d07
0x34b655…2a6f
14 touches
21 conflicts
0xdc204ea3…f1a3
0x34b655…2a6f
12 touches
15 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x50718952…7c75
0x34b655…2a6f
8 touches
6 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity