pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,073,264
← previous block
next block →
recent activity
Analyzing
Block #95,073,264
12 transactions · 12 stateful · 2026-08-11 13:28:18 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,073,264
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
execOrders
#4
updatePrices
#5
0x6df9e92b
· blocks 3
#7
execFwdPositionOps
#10
setData
#11
0x59558d29
#6
0x6df9e92b
· blocks 2
#8
0x6df9e92b
· blocks 1
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a3a7c1…1e2b
0x0cc9b2…7777
8 touches
6 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0002
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0003
0x019883…2a9a
8 touches
6 conflicts
0xa10c86f8…4b74
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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:
MONI (MONI)
6 conflicts on slot
0x99a3a7c17c…081e2b
Audit this contract →
← previous block
·
next block →
recent activity