pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,557,749
← previous block
next block →
recent activity
Analyzing
Block #95,557,749
12 transactions · 10 stateful · 2026-08-13 06:18:48 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,557,749
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
#2
0xab083028
#3
0x4d8dc985
· blocks 1
#4
updatePrices
#7
updateDataFeedsValuesPartial
#8
0x6a7d6240
#9
cancelTournament
#10
setData
#11
0x59558d29
#5
0x5acec890
· blocks 1
#6
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d33617c…4a38
0x34b655…2a6f
4 touches
1 conflict
0x7dfe7788…8d9f
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x13b4fee6…c0e6
0x34b655…2a6f
2 touches
0 conflicts
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
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
0x5d33617c61…124a38
Audit this contract →
← previous block
·
next block →
recent activity