pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,773,362
← previous block
next block →
recent activity
Analyzing
Block #92,773,362
10 transactions · 10 stateful · 2026-08-03 12:21:39 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
#92,773,362
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
executeBatch
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0x59558d29
#9
0xc7e3ec2c
#3
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
2 touches
0 conflicts
0x3a473699…6159
0x754704…b603
2 touches
0 conflicts
0x8434d4d0…d5d8
0x754704…b603
2 touches
0 conflicts
0xa9fde395…e204
0x99c7a7…8bf0
2 touches
0 conflicts
0xb3faae62…90d9
0x99c7a7…8bf0
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:
0xe52b1424…bb7230
1 conflict on slot
0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block
·
next block →
recent activity