pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,045,737
← previous block
next block →
recent activity
Analyzing
Block #71,045,737
14 transactions · 10 stateful · 2026-04-28 08:37:19 UTC
Parallelism
79
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,045,737
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
#2
exactInput
#3
updatePrices
#4
execPerpOps
#5
execPerpOps
#6
0x98717539
#7
exactInputSingle
#8
0xd53e7c84
#9
0x0c7abd22
· blocks 1
#12
0x69f07237
#13
setData
#10
0x6463ffd1
· blocks 1
#11
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0dec7e8b…df6d
0x065c9d…c394
4 touches
1 conflict
0x4a962296…cdcc
0x065c9d…c394
4 touches
1 conflict
0x20732973…9666
0x065c9d…c394
3 touches
1 conflict
0x38ffbee1…1e78
0x065c9d…c394
3 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0002
0x63e48b…53f2
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
0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block
·
next block →
recent activity