pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,526,802
← previous block
next block →
recent activity
Analyzing
Block #98,526,802
12 transactions · 12 stateful · 2026-08-23 16:35:07 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,526,802
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
#3
execOrders
#4
0x6a8b21b3
· blocks 1
#6
0x59558d29
#7
updatePrices
#8
execFwdPositionOpsV2
· blocks 1
#9
0x3f5c179b
#10
setData
#5
0x6a8b21b3
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x461661b9…f714
0x34b655…2a6f
2 touches
0 conflicts
0x4c1c61eb…6992
0x34b655…2a6f
2 touches
0 conflicts
0x5e13521a…8169
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity