pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,403,541
← previous block
next block →
recent activity
Analyzing
Block #92,403,541
8 transactions · 8 stateful · 2026-08-02 05:20:26 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,403,541
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
setData
#5
0x94defb17
· blocks 1
#7
0x59558d29
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05f46979…2fea
0x7b9256…1fb2
4 touches
1 conflict
0x05f46979…2feb
0x7b9256…1fb2
4 touches
1 conflict
0x05f46979…2fee
0x7b9256…1fb2
4 touches
1 conflict
0xe62015c4…043e
0x7b9256…1fb2
4 touches
1 conflict
0xe62015c4…043f
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
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:
0x7b9256fd…e21fb2
1 conflict on slot
0x05f469796c…392fea
Audit this contract →
← previous block
·
next block →
recent activity