pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#78,363,105
← previous block
next block →
recent activity
Analyzing
Block #78,363,105
12 transactions · 10 stateful · 2026-06-01 05:58:55 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
#78,363,105
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
batchUpdate
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x3f5c179b
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
createGame
#11
0x6a1d2017
#2
batchUpdate
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01e8f862…6967
0x065c9d…c394
2 touches
0 conflicts
0x348a181b…f831
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x86e67539…ace7
0x065c9d…c394
2 touches
0 conflicts
0xa5d80d00…b6b3
0x065c9d…c394
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xce827910a4…82ff22
Audit this contract →
← previous block
·
next block →
recent activity