← previous blocknext block →recent activity
Analyzing
Block #87,596,736
36 transactions · 33 stateful · 2026-07-14 00:58:41 UTC
Parallelism
61/100
Blocked
58%
Avg conflicts / tx
2.75
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,596,736 · 36 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w112w213w314w415w516w617w718w819w920w1021w1126w327w1229w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
22 touches
55 conflicts
0x26050074…6967
0x34b655…2a6f
20 touches
45 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
18 touches
36 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
18 touches
36 conflicts
0x84d74093…7808
0x34b655…2a6f
18 touches
36 conflicts
0x9407f89d…82ff
0x34b655…2a6f
18 touches
36 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
18 touches
36 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity