pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,506,986
← previous block
next block →
recent activity
Analyzing
Block #73,506,986
7 transactions · 6 stateful · 2026-05-09 17:58:01 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,506,986
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x69ff7620
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b4d64bb…c98d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x3b8bf5e5…4ae3
0x34b655…2a6f
2 touches
0 conflicts
0x5d28424b…2e40
0x34b655…2a6f
2 touches
0 conflicts
0x642dcd46…cb2e
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:
0x34b6552d…112a6f
1 conflict on slot
0x3b4d64bb81…4fc98d
Audit this contract →
← previous block
·
next block →
recent activity