pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,679,490
← previous block
next block →
recent activity
Analyzing
Block #73,679,490
9 transactions · 8 stateful · 2026-05-10 13:10:13 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,679,490
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5339c59f
· blocks 2
#3
0x5339c59f
#6
0x5339c59f
#7
0x6a00842c
#8
setData
#4
0x5339c59f
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x6e0ce9d7…bce9
0x065c9d…c394
2 touches
0 conflicts
0x9779352a…51ed
0x065c9d…c394
2 touches
0 conflicts
0xade2ada8…c261
0x065c9d…c394
2 touches
0 conflicts
0xfcaa8dda…f46f
0x065c9d…c394
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity