pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,483,640
← previous block
next block →
recent activity
Analyzing
Block #92,483,640
13 transactions · 11 stateful · 2026-08-02 12:03:18 UTC
Parallelism
85
/100
Blocked
27
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,483,640
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
0x94defb17
· blocks 1
#8
forward
#9
execFwdPositionOps
· blocks 1
#11
setData
#12
0x59558d29
#2
0x5acec890
#7
0x94defb17
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb449e84a…bb5b
0x968279…9342
4 touches
1 conflict
0x69a4526e…8401
0x968279…9342
4 touches
1 conflict
0x69a4526e…8402
0x968279…9342
4 touches
1 conflict
0x69a4526e…8405
0x968279…9342
4 touches
1 conflict
0x69a4526e…8406
0x968279…9342
4 touches
1 conflict
0x69a4526e…8408
0x968279…9342
4 touches
1 conflict
0xb449e84a…bb58
0x968279…9342
4 touches
1 conflict
0xb449e84a…bb59
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
0xb449e84a45…d9bb5b
Audit this contract →
← previous block
·
next block →
recent activity