pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,202,086
← previous block
next block →
recent activity
Analyzing
Block #92,202,086
10 transactions · 8 stateful · 2026-08-01 12:27:17 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,202,086
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
interchainTransfer
#4
setData
#5
exactInputSingle
#6
0x0f6795d9
· blocks 1
#8
0x6a6de69c
#9
0x59558d29
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x02ec1927…6d7d
0x34b655…2a6f
4 touches
1 conflict
0x1565183a…e0a0
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
0x34b655…2a6f
4 touches
1 conflict
0x1a60e982…975e
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot
0xf63c2a2b51…78bc60
Audit this contract →
← previous block
·
next block →
recent activity