pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,809,735
← previous block
next block →
recent activity
Analyzing
Block #73,809,735
8 transactions · 5 stateful · 2026-05-11 03:48:27 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,809,735
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a015203
#2
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a015203
#6
setData
#7
0x6a015203
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b97d40a…09ed
0x34b655…2a6f
4 touches
1 conflict
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0x129ba946…48ab
0x34b655…2a6f
4 touches
1 conflict
0x0fa5e7bf…a4da
0x34b655…2a6f
2 touches
0 conflicts
0x220f4f84…15f8
0x34b655…2a6f
2 touches
0 conflicts
0x313f2565…5b00
0x34b655…2a6f
2 touches
0 conflicts
0x578e7f66…1b56
0x34b655…2a6f
2 touches
0 conflicts
0x5d70606a…1d53
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
0x7b97d40a0c…6409ed
Audit this contract →
← previous block
·
next block →
recent activity