pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,204,758
← previous block
next block →
recent activity
Analyzing
Block #73,204,758
9 transactions · 7 stateful · 2026-05-08 08:27:01 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,204,758
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 1
#6
0x69fd9ecd
#7
0xeffdedb0
#8
setData
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x61337b97…e0ff
0x065c9d…c394
2 touches
0 conflicts
0xde8d8f12…61f9
0x065c9d…c394
2 touches
0 conflicts
0xfa68a80c…a970
0x065c9d…c394
2 touches
0 conflicts
0x55b4ed22…fcc8
0x34b655…2a6f
2 touches
0 conflicts
0x6a4f6db4…d702
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity