pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#78,362,051
← previous block
next block →
recent activity
Analyzing
Block #78,362,051
11 transactions · 8 stateful · 2026-06-01 05:51:56 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#78,362,051
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x3f5c179b
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
0x510a3b…5947
#3
0x6ad2e98b
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x9c11d943…f33a
0x0555e3…2b9c
2 touches
0 conflicts
0x170caa34…2d58
0x065c9d…c394
2 touches
0 conflicts
0x8fd71db9…2ea1
0x065c9d…c394
2 touches
0 conflicts
0x9edcef2a…e901
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
0x52e6914362…6e95ad
Audit this contract →
← previous block
·
next block →
recent activity