pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,538,709
← previous block
next block →
recent activity
Analyzing
Block #93,538,709
7 transactions · 7 stateful · 2026-08-06 04:32:10 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,538,709
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
repayWithCollateral
#5
0x6a740ec2
#6
setData
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4722
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x228ac8a1…a607
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3bb514bf…2967
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x0ddfdaf2af…269e00
Audit this contract →
← previous block
·
next block →
recent activity