pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,161,911
← previous block
next block →
recent activity
Analyzing
Block #109,161,911
13 transactions · 13 stateful · 2026-09-29 23:02:18 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,161,911
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8cda051d
#2
setData
· blocks 1
#3
0x61d59c2d
#4
0x59558d29
#5
0x5acec890
· blocks 1
#6
execOrders
#7
execPerpOps
#9
0x3f5c179b
#10
forward
#11
execFwdPositionOpsV2
#8
0x0c7abd22
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
8
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0381e404…e3b1
0x34b655…2a6f
2 touches
0 conflicts
0x09ddd7e2…d284
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x05006bd2…56ea
0x508254…98bd
2 touches
0 conflicts
0x3a663e9a…a9c5
0x508254…98bd
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity