pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,060,196
← previous block
next block →
recent activity
Analyzing
Block #102,060,196
11 transactions · 10 stateful · 2026-09-05 01:56:52 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
#102,060,196
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
0x928e4afa
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
· blocks 2
#8
0x6a9b76e7
#10
execOrders
#7
execFwdPositionOpsV2
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x81159843…e3b5
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
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
0x1a3d2527fb…8a8ca0
Audit this contract →
← previous block
·
next block →
recent activity