pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,267,281
← previous block
next block →
recent activity
Analyzing
Block #93,267,281
9 transactions · 7 stateful · 2026-08-05 05:47:33 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,267,281
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x94defb17
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#3
0x94defb17
· blocks 1
#4
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce72ece5…88d1
0x968279…9342
6 touches
3 conflicts
0xce72ece5…88d2
0x968279…9342
6 touches
3 conflicts
0xce72ece5…88d4
0x968279…9342
6 touches
3 conflicts
0xf48a8c63…0afb
0x968279…9342
6 touches
3 conflicts
0xf48a8c63…0afc
0x968279…9342
6 touches
3 conflicts
0xf48a8c63…0aff
0x968279…9342
6 touches
3 conflicts
0xf48a8c63…0b00
0x968279…9342
6 touches
3 conflicts
0xf48a8c63…0b01
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0xce72ece5ee…6a88d1
Audit this contract →
← previous block
·
next block →
recent activity