pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,914,717
← previous block
next block →
recent activity
Analyzing
Block #97,914,717
11 transactions · 10 stateful · 2026-08-21 13:04:33 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,914,717
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x6ad2e98b
#3
execOrders
· blocks 1
#5
0x5acec890
· blocks 1
#6
forward
#8
setData
#9
0x59558d29
#10
0x59558d29
#4
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x7d89b4c5…dacf
0x34b655…2a6f
4 touches
1 conflict
0x3b2dfb32…949b
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x958db160…cff9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x0d8152a0…f7f4
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
0x309f47c03f…49e1cf
Audit this contract →
← previous block
·
next block →
recent activity