pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,015,665
← previous block
next block →
recent activity
Analyzing
Block #98,015,665
12 transactions · 12 stateful · 2026-08-21 21:36:52 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,015,665
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
execOrders
#3
transfer
#4
0x59558d29
#5
executeBatch
#6
execOrders
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
setData
#10
execOrders
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0a9d9c98…d0e0
0x34b655…2a6f
2 touches
0 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x41ae5cf3…554d
0x34b655…2a6f
2 touches
0 conflicts
0x46abeefb…fc9c
0x34b655…2a6f
2 touches
0 conflicts
0x63726607…4e47
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:
0x34014398…d1768f
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity