pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,328,666
← previous block
next block →
recent activity
Analyzing
Block #73,328,666
8 transactions · 7 stateful · 2026-05-08 22:11:24 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,328,666
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#4
updateFeeds
#5
0x69fe6003
#6
0xeffdedb0
#7
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x32ee90db…decc
0x34b655…2a6f
2 touches
0 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
2 touches
0 conflicts
0x42446806…33dd
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
0x1b9e654ec8…aa0a08
Audit this contract →
← previous block
·
next block →
recent activity