pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,498,216
← previous block
next block →
recent activity
Analyzing
Block #72,498,216
8 transactions · 8 stateful · 2026-05-05 02:01:23 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,498,216
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0xed82b078
· blocks 1
#5
0x69f94fea
#6
setData
#7
0x39435dac
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00c0824e…5b7d
0x065c9d…c394
2 touches
0 conflicts
0x0d1d6b3f…08d6
0x065c9d…c394
2 touches
0 conflicts
0x3ddd2482…d163
0x065c9d…c394
2 touches
0 conflicts
0x4db1a018…a056
0x065c9d…c394
2 touches
0 conflicts
0x7f7aee09…8126
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
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity