pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,199,528
← previous block
next block →
recent activity
Analyzing
Block #75,199,528
10 transactions · 8 stateful · 2026-05-17 14:20:13 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,199,528
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x719d975a
#5
updateDataFeedsValuesPartial
#6
0xe7be4706
#7
updatePriceFeedsIfNecessary
#8
setData
#9
0x39435dac
#2
0x0c7abd22
· blocks 1
#4
execute
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
0xd5a25205…6459
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xb4c56c53…93f1
0xd32edf…ff58
3 touches
1 conflict
0x04a28924…2196
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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:
ShMonad (shMON)
1 conflict on slot
0xd5a2520591…976459
Audit this contract →
← previous block
·
next block →
recent activity