← previous blocknext block →recent activity
Analyzing
Block #87,318,539
40 transactions · 36 stateful · 2026-07-12 17:57:22 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
2.58
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,318,539 · 40 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
1w05w08w19w211w012w113w214w215w316w417w520w821w923w424w528w231w332w433w536w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0x80fd3987…2314
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
12 touches
15 conflicts
0xad0c145d…72b3
0xa6afd3…d132
10 touches
10 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x94ba9c4a…41d8
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity