pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,420,217
← previous block
next block →
recent activity
Analyzing
Block #98,420,217
10 transactions · 10 stateful · 2026-08-23 07:33:09 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,420,217
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
0x5acec890
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xe3ae148c7d…ee7cdd
Audit this contract →
← previous block
·
next block →
recent activity