pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,857,010
← previous block
next block →
recent activity
Analyzing
Block #92,857,010
9 transactions · 9 stateful · 2026-08-03 19:22:38 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,857,010
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
executeBatch
#5
0x0f6795d9
#6
0x94defb17
· blocks 1
#8
setData
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4fb7d50…7d7c
0x968279…9342
4 touches
1 conflict
0xb4fb7d50…7d7d
0x968279…9342
4 touches
1 conflict
0xb4fb7d50…7d7f
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x472e4869…7fb8
0x968279…9342
4 touches
1 conflict
0x472e4869…7fb9
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
0xb4fb7d5097…8f7d7c
Audit this contract →
← previous block
·
next block →
recent activity