pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,963,851
← previous block
next block →
recent activity
Analyzing
Block #92,963,851
10 transactions · 9 stateful · 2026-08-04 04:20:11 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,963,851
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
0x785f5745
· blocks 1
#5
execFwdPositionOps
#6
0x57368ddf
#7
execFwdPositionOps
#8
0x6a7168f3
#9
setData
#4
0x785f5745
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0001
0xbab229…9388
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
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
0x5860c4f397…270c39
Audit this contract →
← previous block
·
next block →
recent activity