← previous blocknext block →recent activity
Analyzing
Block #87,639,147
53 transactions · 37 stateful · 2026-07-14 05:42:16 UTC
Parallelism
79/100
Blocked
70%
Avg conflicts / tx
1.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,639,147 · 53 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w29w310w411w312w317w518w644w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x35c5c9b1…a917
0xd32edf…ff58
13 touches
21 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
8 touches
6 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
8 touches
6 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity