pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,856,033
← previous block
next block →
recent activity
Analyzing
Block #93,856,033
10 transactions · 10 stateful · 2026-08-07 07:07:26 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,856,033
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
execFwdPositionOps
· blocks 2
#6
0x29eed2d3
#7
execOrders
#8
setData
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x1c5968c7…708a
0x34b655…2a6f
4 touches
1 conflict
0x673e2e56…9f5d
0x34b655…2a6f
4 touches
1 conflict
0x6f97afda…faec
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb36066f3…ae65
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
0xfd42a6b911…394c81
Audit this contract →
← previous block
·
next block →
recent activity