pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,542,611
← previous block
next block →
recent activity
Analyzing
Block #95,542,611
12 transactions · 10 stateful · 2026-08-13 05:02:40 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,542,611
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
0x94defb17
· blocks 1
#8
setData
#9
exactInputSingle
#10
0x59558d29
#11
0x61d59c2d
#5
0x0f6795d9
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73da210e…4a9d
0x968279…9342
4 touches
1 conflict
0x276eb86e…daee
0x968279…9342
4 touches
1 conflict
0x276eb86e…daf0
0x968279…9342
4 touches
1 conflict
0x73da210e…4a96
0x968279…9342
4 touches
1 conflict
0x73da210e…4a97
0x968279…9342
4 touches
1 conflict
0x73da210e…4a9a
0x968279…9342
4 touches
1 conflict
0x73da210e…4a9b
0x968279…9342
4 touches
1 conflict
0x038b9243…553d
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:
0x96827978…f09342
1 conflict on slot
0x73da210e8f…2d4a9d
Audit this contract →
← previous block
·
next block →
recent activity