pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,176,397
← previous block
next block →
recent activity
Analyzing
Block #73,176,397
8 transactions · 7 stateful · 2026-05-08 05:18:07 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,176,397
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x121eab2f
· blocks 3
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
setData
#5
0xed82b078
· blocks 2
#6
0xed82b078
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x47b9a106…6951
0x065c9d…c394
4 touches
1 conflict
0x8a485a15…dc73
0x065c9d…c394
3 touches
1 conflict
0xbdb22da5…7460
0x065c9d…c394
3 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
2 touches
0 conflicts
0x9304b4d8…8b15
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:
0x065c9d28…a9c394
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity