← previous blocknext block →recent activity
Analyzing
Block #87,918,564
70 transactions · 45 stateful · 2026-07-15 12:51:15 UTC
Parallelism
76/100
Blocked
71%
Avg conflicts / tx
1.74
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,918,564 · 70 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w412w013w116w219w020w125w526w628w752w754w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
14 touches
21 conflicts
0x3b71bb7c…8dab
0xd32edf…ff58
11 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x1dddd7ef…8f05
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity