← previous blocknext block →recent activity
Analyzing
Block #87,504,041
38 transactions · 30 stateful · 2026-07-13 14:37:55 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
1.5
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,504,041 · 38 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
1w02w13w24w05w17w312w013w117w118w219w320w425w626w727w828w930w433w1035w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x2089dcc1…8f89
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc3688185…9b36
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5a011b4a…30f7
0xd32edf…ff58
7 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x74dae4f2…f2d8
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity