pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,079,716
← previous block
next block →
recent activity
Analyzing
Block #102,079,716
11 transactions · 11 stateful · 2026-09-05 03:35:58 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
#102,079,716
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#4
0xab083028
#5
0xab083028
#6
forward
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#10
handleOps
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6875750…9542
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8feb2121…031a
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xbb9ab337…f4ec
0x34b655…2a6f
4 touches
1 conflict
0xcdcc920e…c0dc
0x34b655…2a6f
4 touches
1 conflict
0xddf10453…d774
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
0xe6875750e1…ed9542
Audit this contract →
← previous block
·
next block →
recent activity