← previous blocknext block →recent activity
Analyzing
Block #87,714,262
56 transactions · 38 stateful · 2026-07-14 14:04:34 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.77
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,714,262 · 56 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w212w013w114w133w738w839w940w1042w343w1145w446w547w248w351w1252w1353w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x8b8a50e1…b5dc
0x34b655…2a6f
12 touches
15 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0x9407f89d…82ff
0x34b655…2a6f
12 touches
15 conflicts
0xd8834cf3…0004
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
28 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity