← previous blocknext block →recent activity
Analyzing
Block #86,951,485
36 transactions · 32 stateful · 2026-07-11 01:03:26 UTC
Parallelism
58/100
Blocked
75%
Avg conflicts / tx
2.56
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,951,485 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w17w210w011w112w213w314w415w516w617w718w819w921w222w123w324w430w1033w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
10 touches
10 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity