pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,397,344
← previous block
next block →
recent activity
Analyzing
Block #108,397,344
7 transactions · 7 stateful · 2026-09-27 06:46:34 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,397,344
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x3f5c179b
#3
0x84403c1b
· blocks 1
#5
execFwdPositionOpsV2
#6
setData
#4
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd33a3d56…2ae3
0x34b655…2a6f
4 touches
1 conflict
0x2292983d…dbee
0x34b655…2a6f
4 touches
1 conflict
0xfc51df41…9981
0x34b655…2a6f
4 touches
1 conflict
0xb280b12c…bd9c
0x34b655…2a6f
4 touches
1 conflict
0xbe9a3422…22ec
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0xaba6578d…bd48
0x34b655…2a6f
2 touches
0 conflicts
0xdb3937e8…23cb
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
0xd33a3d561b…5f2ae3
Audit this contract →
← previous block
·
next block →
recent activity