pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,929,429
← previous block
next block →
recent activity
Analyzing
Block #98,929,429
10 transactions · 8 stateful · 2026-08-25 02:51:34 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
#98,929,429
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x32d01e04
#3
execOrders
· blocks 1
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
transferWithAuthorization
#7
setData
#8
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
2 touches
0 conflicts
0x2689e92a…b2a1
0x34b655…2a6f
2 touches
0 conflicts
0x3dad3b45…8edb
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x931975c27f…80b7b3
Audit this contract →
← previous block
·
next block →
recent activity