pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,006,940
← previous block
next block →
recent activity
Analyzing
Block #102,006,940
11 transactions · 11 stateful · 2026-09-04 21:27:12 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,006,940
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0xab083028
#3
0x5acec890
#5
0x5acec890
#6
0x59558d29
#7
setData
#9
0x6a9b3828
#4
0x5acec890
· blocks 1
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
8
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x3967a4c9…c000
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0fd42f9f…126e
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x28c4cb5d…b55e
0x34b655…2a6f
2 touches
0 conflicts
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
0x4f125e8922…507ee0
Audit this contract →
← previous block
·
next block →
recent activity