pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,240,367
← previous block
next block →
recent activity
Analyzing
Block #77,240,367
13 transactions · 7 stateful · 2026-05-27 01:12:24 UTC
Parallelism
77
/100
Blocked
29
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,240,367
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6a164570
#5
0x6c05cd2b
#6
updateDataFeedsValuesPartial
#7
execOrders
#8
0x6a164570
#9
0x6a164570
#10
setData
#11
jMMeC
#12
jMMeC
#2
0x0c7abd22
· blocks 1
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x077c3388…b5c8
0x065c9d…c394
3 touches
1 conflict
0x4acd9ec1…ae0d
0x065c9d…c394
3 touches
1 conflict
0xa856d365…4465
0xd32edf…ff58
3 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x77ed432f03…d6fa04
Audit this contract →
← previous block
·
next block →
recent activity