← previous blocknext block →recent activity
Analyzing
Block #87,718,690
114 transactions · 58 stateful · 2026-07-14 14:34:20 UTC
Parallelism
82/100
Blocked
67%
Avg conflicts / tx
1.82
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,718,690 · 114 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w010w113w316w417w519w620w741w8103w9104w10107w2108w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x015c28a0…37da
0x34b655…2a6f
14 touches
21 conflicts
0x0ba865dd…a249
0x34b655…2a6f
14 touches
21 conflicts
0xbf694a56…459d
0xd32edf…ff58
13 touches
21 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
120 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity