pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,649,581
← previous block
next block →
recent activity
Analyzing
Block #73,649,581
10 transactions · 10 stateful · 2026-05-10 09:48:24 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,649,581
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x54390b8b
· blocks 2
#3
0x98717539
#4
multicall
#5
updateDataFeedsValuesPartial
#6
setData
#8
0x0c7abd22
#9
forward
#2
0x42dd8743
· blocks 1
#7
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0xde75dc4e…a349
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…003d
0x122c0d…e3fa
2 touches
0 conflicts
0x41b7e4b2…5ef1
0x122c0d…e3fa
2 touches
0 conflicts
0x45d619d3…1678
0x122c0d…e3fa
2 touches
0 conflicts
0x45d619d3…1679
0x122c0d…e3fa
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0xc9e9752290…9c3519
Audit this contract →
← previous block
·
next block →
recent activity