pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,445,514
← previous block
next block →
recent activity
Analyzing
Block #105,445,514
12 transactions · 11 stateful · 2026-09-16 23:03:50 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,445,514
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrder
· blocks 1
#3
0x5acec890
#4
0x928e4afa
#5
0x59558d29
#6
0x6aab2059
#7
setData
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
0x0c7abd22
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40c1915…55ed
0x34b655…2a6f
4 touches
1 conflict
0x66a5e30d…65af
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1c4fbcbc…d11d
0x34b655…2a6f
2 touches
0 conflicts
0x281d1917…46ff
0x34b655…2a6f
2 touches
0 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
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
0xc40c191580…c155ed
Audit this contract →
← previous block
·
next block →
recent activity