pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,726,841
← previous block
next block →
recent activity
Analyzing
Block #95,726,841
10 transactions · 9 stateful · 2026-08-13 20:30:21 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,726,841
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
updatePrices
#6
0xcffefd2e
· blocks 2
#9
setData
#2
0xab083028
#7
0xcffefd2e
#8
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x82027703…ae78
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xb5a74b91…bde4
0x34b655…2a6f
4 touches
1 conflict
0xc051ceff…3452
0x34b655…2a6f
4 touches
1 conflict
0xc0a4133e…6110
0x34b655…2a6f
4 touches
1 conflict
0xcb10fd4e…6167
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xf4c9a0dfc5…fcdcd5
Audit this contract →
← previous block
·
next block →
recent activity