← previous blocknext block →recent activity
Analyzing
Block #87,785,643
31 transactions · 29 stateful · 2026-07-14 22:02:14 UTC
Parallelism
42/100
Blocked
62%
Avg conflicts / tx
4.97
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,785,643 · 31 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1317w1418w1528w1629w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
36 touches
153 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
32 touches
120 conflicts
0x28c62bca…b746
0x34b655…2a6f
32 touches
120 conflicts
0x5b145de0…367c
0xc8689a…ee79
32 touches
120 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x9ae859db…2d84
0x34b655…2a6f
32 touches
120 conflicts
0x9fd37234…2731
0x34b655…2a6f
32 touches
120 conflicts
0xb9801357…5fef
0x34b655…2a6f
16 touches
28 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
153 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity