← previous blocknext block →recent activity
Analyzing
Block #87,758,325
21 transactions · 17 stateful · 2026-07-14 18:59:25 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,758,325 · 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
1w02w15w06w17w28w39w410w011w118w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x3fde350e…8d43
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x344bc09a…942f
0x34b655…2a6f
10 touches
10 conflicts
0x587911c7…9e01
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x81daadf1…338f
0x34b655…2a6f
10 touches
10 conflicts
0x86f95c40…5bef
0x34b655…2a6f
10 touches
10 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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity