← previous blocknext block →recent activity
Analyzing
Block #87,710,541
57 transactions · 43 stateful · 2026-07-14 13:39:39 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
2.33
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,710,541 · 57 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
1w02w03w14w25w210w011w118w119w020w121w223w324w425w526w633w234w336w437w939w1040w1143w245w346w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7837c02d…0965
0x34b655…2a6f
12 touches
15 conflicts
0xebe9512d…5162
0x34b655…2a6f
12 touches
15 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
10 touches
10 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity