pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,161,567
← previous block
next block →
recent activity
Analyzing
Block #109,161,567
11 transactions · 10 stateful · 2026-09-29 23:00:35 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,161,567
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x61d59c2d
· blocks 1
#3
0xab083028
#5
execute
#6
execFwdPositionOpsV2
#7
forward
#8
execFwdPositionOpsV2
#9
commit
#10
setData
#2
0x303bd359
· blocks 1
#4
0x203bd359
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x00000000…0003
0x125f12…a50b
4 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
4 touches
1 conflict
0x05006bd2…56ea
0x508254…98bd
4 touches
1 conflict
0x25b1c19a…6d24
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0xd9c799c9…d0d9
0x508254…98bd
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:
0x508254c8…4a98bd
1 conflict on slot
0xe1c4d8e8bd…deffa8
Audit this contract →
← previous block
·
next block →
recent activity