pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,075,209
← previous block
next block →
recent activity
Analyzing
Block #96,075,209
12 transactions · 9 stateful · 2026-08-15 01:43:03 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,075,209
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0x41a8f47c
#3
0x6b8f732b
· blocks 1
#4
0x6b8f732b
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
setData
#10
withdraw
#11
execOrders
#5
0x6b8f732b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x883f9ec6…3664
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
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
0xd9f1e40f03…3209a3
Audit this contract →
← previous block
·
next block →
recent activity