pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,678,456
← previous block
next block →
recent activity
Analyzing
Block #85,678,456
11 transactions · 10 stateful · 2026-07-05 03:20:35 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,678,456
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x62be7533
#5
0x0f6795d9
#6
0x3f5c179b
#7
0x3f5c179b
#9
0x0f6795d9
#10
setData
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3f58353…05be
0x065c9d…c394
4 touches
1 conflict
0x9fb8056e…f487
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdc3144a4…87ec
0x065c9d…c394
3 touches
1 conflict
0x7e19f55d…8297
0x065c9d…c394
3 touches
1 conflict
0x481daa7d…8e66
0x065c9d…c394
2 touches
0 conflicts
0xbb591a65…b142
0x065c9d…c394
2 touches
0 conflicts
0xf15ac27b…dd2e
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
0xf3f58353fc…ea05be
Audit this contract →
← previous block
·
next block →
recent activity