pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,085,398
← previous block
next block →
recent activity
Analyzing
Block #95,085,398
12 transactions · 11 stateful · 2026-08-11 14:29:21 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,085,398
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x222d4ad6
#4
executeBatch
#5
0x94defb17
· blocks 1
#7
forward
#8
0x0f6795d9
· blocks 1
#10
transfer
#11
setData
#6
0x94defb17
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27c74c4e…d316
0x968279…9342
4 touches
1 conflict
0x27c74c4e…d318
0x968279…9342
4 touches
1 conflict
0x42847afe…451e
0x968279…9342
4 touches
1 conflict
0x42847afe…451f
0x968279…9342
4 touches
1 conflict
0x42847afe…4521
0x968279…9342
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x87d1b778…dcfe
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
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
0x27c74c4e13…a5d316
Audit this contract →
← previous block
·
next block →
recent activity