← previous blocknext block →recent activity
Analyzing
Block #87,504,286
46 transactions · 38 stateful · 2026-07-13 14:39:36 UTC
Parallelism
70/100
Blocked
71%
Avg conflicts / tx
2.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,504,286 · 46 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
1w07w08w19w110w011w112w213w314w415w516w617w718w819w920w122w325w326w427w532w635w737w941w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
20 touches
45 conflicts
0x1d946063…ba90
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x3a6290da…e683
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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: 0xc1ff9fef…f4b0fc
45 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity