pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,422,492
← previous block
next block →
recent activity
Analyzing
Block #93,422,492
11 transactions · 11 stateful · 2026-08-05 18:47:56 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,422,492
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execFwdPositionOps
#3
repayWithCollateral
#4
0x94defb17
· blocks 1
#6
0xed82b078
#7
execFwdPositionOps
#8
setData
#9
execOrders
#10
0x59558d29
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9ca0495…3f4d
0x968279…9342
4 touches
1 conflict
0x047bd283…c122
0x968279…9342
4 touches
1 conflict
0x047bd283…c123
0x968279…9342
4 touches
1 conflict
0x047bd283…c126
0x968279…9342
4 touches
1 conflict
0x047bd283…c127
0x968279…9342
4 touches
1 conflict
0x047bd283…c129
0x968279…9342
4 touches
1 conflict
0xa9ca0495…3f4a
0x968279…9342
4 touches
1 conflict
0xa9ca0495…3f4b
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
0xa9ca049568…e13f4d
Audit this contract →
← previous block
·
next block →
recent activity