← previous blocknext block →recent activity
Analyzing
Block #87,504,195
33 transactions · 30 stateful · 2026-07-13 14:38:58 UTC
Parallelism
58/100
Blocked
63%
Avg conflicts / tx
1.88
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,504,195 · 33 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
1w02w04w05w16w07w110w011w112w213w214w317w418w519w620w721w123w125w826w927w1028w1129w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x1d946063…ba90
0x34b655…2a6f
10 touches
10 conflicts
0xd3040f4d…54ca
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x82fddc68…f757
0x34b655…2a6f
8 touches
6 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity