← previous blocknext block →recent activity
Analyzing
Block #87,708,169
63 transactions · 47 stateful · 2026-07-14 13:23:46 UTC
Parallelism
64/100
Blocked
77%
Avg conflicts / tx
3.68
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,708,169 · 63 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w07w110w211w312w414w518w252w453w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
36 touches
153 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
18 touches
36 conflicts
0x3b679ba3…b050
0x34b655…2a6f
14 touches
21 conflicts
0x48315f67…c1a6
0x34b655…2a6f
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
14 touches
21 conflicts
0x030bd256…c5c3
0x34b655…2a6f
14 touches
21 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity