← previous blocknext block →recent activity
Analyzing
Block #87,759,987
30 transactions · 28 stateful · 2026-07-14 19:10:33 UTC
Parallelism
37/100
Blocked
68%
Avg conflicts / tx
6.27
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,759,987 · 30 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
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1621w1722w1829w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0x2f461725…5ab2
0x34b655…2a6f
24 touches
66 conflicts
0x9ae859db…2d84
0x34b655…2a6f
24 touches
66 conflicts
0x747f609d…1555
0x34b655…2a6f
22 touches
55 conflicts
0x5b145de0…367c
0xc8689a…ee79
22 touches
55 conflicts
0xaa643d44…2122
0x34b655…2a6f
22 touches
55 conflicts
0x28c62bca…b746
0x34b655…2a6f
22 touches
55 conflicts
0xe732567d…b65d
0x34b655…2a6f
12 touches
15 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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity