pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,038,618
← previous block
next block →
recent activity
Analyzing
Block #73,038,618
11 transactions · 9 stateful · 2026-05-07 14:01:33 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,038,618
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0x62be7533
#7
0x69fc9bb5
#8
0xeffdedb0
#9
setData
#10
execOrders
#2
0x9036287a
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
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x566fb836…ba37
0x065c9d…c394
2 touches
0 conflicts
0x5cbee3ea…c3c4
0x065c9d…c394
2 touches
0 conflicts
0xabd222d5…cfef
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
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
0xbd7e37a9b5…859eb5
Audit this contract →
← previous block
·
next block →
recent activity