pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,527,185
← previous block
next block →
recent activity
Analyzing
Block #98,527,185
9 transactions · 9 stateful · 2026-08-23 16:37:06 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,527,185
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0x6a8b2229
#4
execOrders
· blocks 2
#6
0x59558d29
#8
setData
#5
execOrders
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x55dee215…26bb
0x34b655…2a6f
4 touches
1 conflict
0xd9c075c9…0a14
0x34b655…2a6f
3 touches
1 conflict
0x09b0dd07…47e5
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x6e3e9f18…f684
0x34b655…2a6f
2 touches
0 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
3 conflicts on slot
0x7de579746e…f0f5ba
Audit this contract →
← previous block
·
next block →
recent activity