pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,554,298
← previous block
next block →
recent activity
Analyzing
Block #95,554,298
11 transactions · 9 stateful · 2026-08-13 06:01:27 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,554,298
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
handleOps
· blocks 1
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
updateTemporalNumericValuesV1
#10
setData
#6
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
4 touches
1 conflict
0x995619c0…f983
0x5afd3e…7620
4 touches
1 conflict
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x6e9b4ab5…a3eb
0x754704…b603
4 touches
1 conflict
0x4bc1abab…5874
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:
Wrapped MON (WMON)
1 conflict on slot
0x5d82c9b53a…be004c
Audit this contract →
← previous block
·
next block →
recent activity