← previous blocknext block →recent activity
Analyzing
Block #87,700,298
78 transactions · 58 stateful · 2026-07-14 12:30:54 UTC
Parallelism
76/100
Blocked
76%
Avg conflicts / tx
3.21
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,700,298 · 78 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w17w08w010w013w116w218w321w522w423w530w132w233w134w236w358w160w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0x70986451…c6bd
0x34b655…2a6f
14 touches
21 conflicts
0x2fcd4130…b4a5
0xc8689a…ee79
14 touches
21 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
14 touches
21 conflicts
0x4b90e63c…c17d
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity