pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,685,462
← previous block
next block →
recent activity
Analyzing
Block #108,685,462
8 transactions · 8 stateful · 2026-09-28 06:57:21 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,685,462
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
#3
0x5acec890
#5
setData
#6
0x61d59c2d
· blocks 1
#4
0x0c7abd22
#7
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05006bd2…56e5
0x508254…98bd
4 touches
1 conflict
0x05006bd2…56ea
0x508254…98bd
4 touches
1 conflict
0x25b1c19a…6d24
0x508254…98bd
4 touches
1 conflict
0x29f3d595…de4b
0x508254…98bd
4 touches
1 conflict
0x29f3d595…de6b
0x508254…98bd
4 touches
1 conflict
0x29f3d595…de87
0x508254…98bd
4 touches
1 conflict
0x29f3d595…de9a
0x508254…98bd
4 touches
1 conflict
0x29f3d595…dea4
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
0x05006bd227…b856e5
Audit this contract →
← previous block
·
next block →
recent activity