← previous blocknext block →recent activity
Analyzing
Block #87,717,047
41 transactions · 38 stateful · 2026-07-14 14:23:21 UTC
Parallelism
54/100
Blocked
66%
Avg conflicts / tx
2.44
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,717,047 · 41 txs across 19 waves · depth 19
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
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w09w116w227w1128w1230w131w1332w1433w336w1538w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x722851f4…73fe
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7525206c…fbd5
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
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
36 conflicts on slot 0x722851f4b1…4173fe
Audit this contract →
← previous block·next block →recent activity