pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,641,673
← previous block
next block →
recent activity
Analyzing
Block #73,641,673
13 transactions · 12 stateful · 2026-05-10 08:55:03 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,641,673
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x6a00485e
#3
updatePrices
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x5bf9264c
#8
0xe7be4706
#9
0x98717539
#10
0x6df9e92b
· blocks 1
#12
0xe9316489
#11
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
2 touches
0 conflicts
0xb82bffbd…c6de
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:
0x3bd359c1…15433a
1 conflict on slot
0x08fdca0ba0…724abf
Audit this contract →
← previous block
·
next block →
recent activity