← previous blocknext block →recent activity
Analyzing
Block #87,355,487
35 transactions · 28 stateful · 2026-07-12 22:04:25 UTC
Parallelism
54/100
Blocked
71%
Avg conflicts / tx
2.66
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,355,487 · 35 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
3w06w18w09w110w211w312w413w514w615w716w817w919w820w923w124w229w1130w1233w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
10 touches
10 conflicts
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0x4de29e1c…661e
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 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