pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,015,848
← previous block
next block →
recent activity
Analyzing
Block #75,015,848
12 transactions · 8 stateful · 2026-05-16 17:54:36 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,015,848
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
handleOps
#4
0x5b05baa2
#5
0x1a945f9c
#6
updateDataFeedsValuesPartial
#7
0x6a08afd4
#8
setData
#9
0xd87163…ac3f
#10
0xcc20ea…c0ed
#11
execute
#2
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x457e046d…6384
0x065c9d…c394
2 touches
0 conflicts
0x4cea0b8b…b730
0x065c9d…c394
2 touches
0 conflicts
0xad0fce64…e2cc
0x065c9d…c394
2 touches
0 conflicts
0xbd039566…f039
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity