pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,519,436
← previous block
next block →
recent activity
Analyzing
Block #74,519,436
11 transactions · 5 stateful · 2026-05-14 10:35:05 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,519,436
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
forward
#4
updateDataFeedsValuesPartial
#5
0x3c19da…2dee
#6
0xf05763…9a62
#7
0x766c5e…6b44
#8
0x31ad3c…796f
#9
setData
#10
0x3a4dc5…8721
#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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x8609ff25…a4b7
0x065c9d…c394
2 touches
0 conflicts
0xb1d57bb7…1037
0x065c9d…c394
2 touches
0 conflicts
0xfbe4e939…fb1e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity