← previous blocknext block →recent activity
Analyzing
Block #87,710,060
71 transactions · 49 stateful · 2026-07-14 13:36:26 UTC
Parallelism
68/100
Blocked
73%
Avg conflicts / tx
3.54
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,710,060 · 71 txs across 23 waves · depth 23
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
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w18w211w312w450w155w459w562w663w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
24 touches
66 conflicts
0xe3321cb6…26de
0x34b655…2a6f
20 touches
45 conflicts
0x197e2da8…f1f4
0x34b655…2a6f
20 touches
45 conflicts
0x3b679ba3…b050
0x34b655…2a6f
20 touches
45 conflicts
0x767799cd…f423
0xc8689a…ee79
20 touches
45 conflicts
0xc03846bb…73b3
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity