pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,572,509
← previous block
next block →
recent activity
Analyzing
Block #95,572,509
12 transactions · 10 stateful · 2026-08-13 07:33:02 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,572,509
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x94defb17
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
execOrders
#8
updateDataFeedsValuesPartial
#9
0x6a7d73a6
#10
updateDataFeedsValuesPartial
#11
setData
#4
0x94defb17
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa39ce2ef…93dc
0x968279…9342
4 touches
1 conflict
0x229ed15d…cae4
0x968279…9342
4 touches
1 conflict
0x229ed15d…cae5
0x968279…9342
4 touches
1 conflict
0x229ed15d…cae8
0x968279…9342
4 touches
1 conflict
0x229ed15d…cae9
0x968279…9342
4 touches
1 conflict
0x229ed15d…caea
0x968279…9342
4 touches
1 conflict
0xa39ce2ef…93d9
0x968279…9342
4 touches
1 conflict
0xa39ce2ef…93da
0x968279…9342
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
0xa39ce2ef64…fc93dc
Audit this contract →
← previous block
·
next block →
recent activity