pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,378,066
← previous block
next block →
recent activity
Analyzing
Block #73,378,066
11 transactions · 10 stateful · 2026-05-09 03:39:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,378,066
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
0x69fead03
#8
0xeffdedb0
#9
setData
#10
0x39435dac
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
4 touches
1 conflict
0xd563f3a1…94b1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x59d1e760…e579
0x34b655…2a6f
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x9125126a…ef1e
0x34b655…2a6f
2 touches
0 conflicts
0xc1a963ef…c582
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xb1927b5859…36f161
Audit this contract →
← previous block
·
next block →
recent activity