pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,647,068
← previous block
next block →
recent activity
Analyzing
Block #73,647,068
9 transactions · 6 stateful · 2026-05-10 09:31:26 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,647,068
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
forward
#8
setData
#2
0x0c7abd22
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
0x55ff7ac9…5dc1
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07e02c84…70fc
0x188d58…ea8e
2 touches
0 conflicts
0x07e02c84…70fd
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a60
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a62
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a63
0x188d58…ea8e
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:
0xd32edf66…9fff58
1 conflict on slot
0x55ff7ac933…865dc1
Audit this contract →
← previous block
·
next block →
recent activity