pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,024,751
← previous block
next block →
recent activity
Analyzing
Block #74,024,751
9 transactions · 8 stateful · 2026-05-12 03:42:33 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,024,751
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
batchUpdate
· blocks 1
#4
batchUpdate
· blocks 2
#8
setData
#5
batchUpdate
#6
batchUpdate
· blocks 1
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x30e87049…4a0e
0x065c9d…c394
2 touches
0 conflicts
0x3f6c5271…01f5
0x065c9d…c394
2 touches
0 conflicts
0x4b04adab…82fb
0x065c9d…c394
2 touches
0 conflicts
0x726eab9a…e12c
0x065c9d…c394
2 touches
0 conflicts
0x77c6b02d…e82a
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: MarginAccount
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity