← previous blocknext block →recent activity
Analyzing
Block #87,703,337
64 transactions · 49 stateful · 2026-07-14 12:51:23 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
2.64
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,703,337 · 64 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w08w09w110w011w112w013w114w215w316w417w518w619w720w827w240w241w145w346w447w548w649w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
12 touches
15 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
10 touches
10 conflicts
0x9b02ba92…7100
0x34b655…2a6f
10 touches
10 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
10 touches
10 conflicts
0x21605a79…d719
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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity