pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,666,092
← previous block
next block →
recent activity
Analyzing
Block #74,666,092
11 transactions · 10 stateful · 2026-05-15 02:58:13 UTC
Parallelism
64
/100
Blocked
40
%
Avg conflicts / tx
0.64
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,666,092
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
approve
#9
setData
#10
approve
#2
flash
· blocks 2
#3
0xed82b078
· blocks 1
#7
batchUpdate
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
4 touches
1 conflict
0x61c3dc12…5724
0x065c9d…c394
3 touches
1 conflict
0x8cb32b24…68d9
0x065c9d…c394
3 touches
1 conflict
0xa0d06272…7893
0x065c9d…c394
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity