← previous blocknext block →recent activity
Analyzing
Block #87,583,092
41 transactions · 38 stateful · 2026-07-13 23:27:25 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
2.51
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,583,092 · 41 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
1w02w03w14w25w37w08w09w010w111w212w313w114w215w316w417w520w225w326w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x57bb625a…286d
0x34b655…2a6f
10 touches
10 conflicts
0x5f34fd08…aeb3
0x34b655…2a6f
10 touches
10 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
10 touches
10 conflicts
0x207b4a17…4084
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity