pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,599,868
← previous block
next block →
recent activity
Analyzing
Block #73,599,868
8 transactions · 7 stateful · 2026-05-10 04:15:06 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,599,868
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x6a0006c2
#6
setData
#7
0x39435dac
#2
0x121eab2f
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
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…000b
0x6c4bfa…a540
4 touches
1 conflict
0x0175b7a6…1db9
0x6c4bfa…a540
4 touches
1 conflict
0x0175b7a6…1dba
0x6c4bfa…a540
4 touches
1 conflict
0x0175b7a6…1dbc
0x6c4bfa…a540
4 touches
1 conflict
0x0c89ea7e…13eb
0x6c4bfa…a540
4 touches
1 conflict
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:
0xc8689a47…62ee79
1 conflict on slot
0xed57bddf8e…bd1abf
Audit this contract →
← previous block
·
next block →
recent activity