pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,491,921
← previous block
next block →
recent activity
Analyzing
Block #102,491,921
10 transactions · 10 stateful · 2026-09-06 14:24:48 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,491,921
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
transferWithAuthorization
#7
execFwdPositionOpsV2
· blocks 1
#9
commit
#2
0x39ecce49
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea613003…a4f0
0xe1c8b7…3022
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4e844eaf…39b0
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5aba66…b29f
4 touches
1 conflict
0xeceef4df…082f
0x7b6ec4…7777
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:
0xe1c8b733…e33022
1 conflict on slot
0xea613003f3…88a4f0
Audit this contract →
← previous block
·
next block →
recent activity