pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,902,772
← previous block
next block →
recent activity
Analyzing
Block #94,902,772
10 transactions · 8 stateful · 2026-08-10 23:09:57 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
#94,902,772
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execFwdPositionOps
#3
executeBatch
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0x59558d29
· blocks 1
#9
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1719c655…6592
0x34b655…2a6f
2 touches
0 conflicts
0x17aad0b2…59d0
0x34b655…2a6f
2 touches
0 conflicts
0x1aea4fdd…0adc
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6214
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity