pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,036,418
← previous block
next block →
recent activity
Analyzing
Block #73,036,418
16 transactions · 9 stateful · 2026-05-07 13:46:54 UTC
Parallelism
88
/100
Blocked
22
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,036,418
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
0x16040cc9
· blocks 1
#11
updateDataFeedsValuesPartial
#12
0x0c7abd22
#13
0x69fc9846
#14
0xeffdedb0
#15
setData
#2
updatePrices
#10
0x16040cc9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x00000000…0000
0x23286a…478c
4 touches
1 conflict
0x00000000…0002
0x23286a…478c
4 touches
1 conflict
0x00000000…0003
0x23286a…478c
4 touches
1 conflict
0x8f953837…7f52
0x3bd359…433a
4 touches
1 conflict
0xcfa1963e…8856
0x91ce82…7777
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
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:
0xd574cae5…037ab1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity