pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,649,616
← previous block
next block →
recent activity
Analyzing
Block #74,649,616
9 transactions · 8 stateful · 2026-05-15 01:07:58 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,649,616
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a067266
#2
0x1ffa3c9b
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
updateTemporalNumericValuesV1
#5
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
setData
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e65164…2bfc
0x065c9d…c394
4 touches
1 conflict
0x35fff115…05d0
0x065c9d…c394
3 touches
1 conflict
0x217c3eed…7523
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x044644fa…f627
0x065c9d…c394
2 touches
0 conflicts
0x3f193efa…ed4d
0x065c9d…c394
2 touches
0 conflicts
0xcd7ee598…308b
0x065c9d…c394
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
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
0x70e65164f9…942bfc
Audit this contract →
← previous block
·
next block →
recent activity