← previous blocknext block →recent activity
Analyzing
Block #87,704,499
70 transactions · 46 stateful · 2026-07-14 12:59:12 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
2.56
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,704,499 · 70 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w113w214w316w417w020w024w026w136w037w138w239w340w452w261w562w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
12 touches
15 conflicts
0x7fd53511…8f76
0x34b655…2a6f
12 touches
15 conflicts
0xa57576bb…e01f
0x34b655…2a6f
12 touches
15 conflicts
0xad09dd03…27d0
0x34b655…2a6f
12 touches
15 conflicts
0xb02dc238…2fca
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity