pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,848,344
← previous block
next block →
recent activity
Analyzing
Block #94,848,344
13 transactions · 11 stateful · 2026-08-10 18:36:13 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,848,344
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
executeBatch
#7
0x94defb17
· blocks 1
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
0x39abec6b
#12
setData
#6
0x3f5c179b
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda58c610…5d31
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x88936bd9…bafc
0x968279…9342
4 touches
1 conflict
0x88936bd9…bafd
0x968279…9342
4 touches
1 conflict
0x88936bd9…bb00
0x968279…9342
4 touches
1 conflict
0x88936bd9…bb01
0x968279…9342
4 touches
1 conflict
0x88936bd9…bb02
0x968279…9342
4 touches
1 conflict
0xda58c610…5d2e
0x968279…9342
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0xda58c6105c…255d31
Audit this contract →
← previous block
·
next block →
recent activity