pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,860,348
← previous block
next block →
recent activity
Analyzing
Block #72,860,348
9 transactions · 8 stateful · 2026-05-06 18:15:04 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,860,348
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
#2
0x69fb859f
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x69fb859f
#6
0xeffdedb0
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b8ffd61…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0756893a…33ea
0x065c9d…c394
2 touches
0 conflicts
0x1f362c07…5dd1
0x065c9d…c394
2 touches
0 conflicts
0x6d916f99…4808
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
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:
0x34b6552d…112a6f
1 conflict on slot
0x3b8ffd6160…92f3ad
Audit this contract →
← previous block
·
next block →
recent activity