pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,987,195
← previous block
next block →
recent activity
Analyzing
Block #75,987,195
12 transactions · 9 stateful · 2026-05-21 06:04:39 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,987,195
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
swapAndForwardERC20
#3
mintCube
#4
0xec2bd3f2
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#9
0x25fb2a…a702
#10
0x2dd987…dd79
#11
0x5e9863…4087
#7
0x6df9e92b
· blocks 1
#8
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x1195cf…64b7
2 touches
0 conflicts
0x00000000…0009
0x1195cf…64b7
2 touches
0 conflicts
0x866bf367…7a60
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a62
0x188d58…ea8e
2 touches
0 conflicts
0x38aa1898…fdf5
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:
Wrapped MON (WMON)
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity