pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,113,015
← previous block
next block →
recent activity
Analyzing
Block #108,113,015
12 transactions · 10 stateful · 2026-09-26 06:55:40 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,113,015
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x9ac0761c
#2
0x59558d29
#3
0xab083028
#4
0x5acec890
#5
0x5acec890
#6
0x928e4afa
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x6ab76c6e
#10
setData
#11
0x07972f…8f26
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1087ebd2…005b
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xa1c62481…2f60
0x065c9d…c394
2 touches
0 conflicts
0xc60f7fee…630f
0x065c9d…c394
2 touches
0 conflicts
0xd6381a12…cb29
0x065c9d…c394
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.
← previous block
·
next block →
recent activity