pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,481,077
← previous block
next block →
recent activity
Analyzing
Block #106,481,077
11 transactions · 11 stateful · 2026-09-20 13:58:16 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,481,077
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#3
0x5acec890
#5
0x59558d29
· blocks 1
#7
execPerpOps
#8
setData
#9
execFwdPositionOpsV2
#10
0x6aafe67b
#4
0x928e4afa
#6
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0ef67310…acdc
0x34b655…2a6f
2 touches
0 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 conflicts
0x2f50c84a…3640
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity