pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,309,866
← previous block
next block →
recent activity
Analyzing
Block #72,309,866
8 transactions · 7 stateful · 2026-05-04 05:06:43 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,309,866
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9036287a
· blocks 2
#2
updateDataFeedsValuesPartial
#4
forward
#6
0x69f829da
#7
setData
#3
0x3f5c179b
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x2e3989e5…e612
0x065c9d…c394
2 touches
0 conflicts
0x36ecae44…6d6f
0x065c9d…c394
2 touches
0 conflicts
0x4e81177f…55e8
0x065c9d…c394
2 touches
0 conflicts
0xdd7c9268…6e90
0x065c9d…c394
2 touches
0 conflicts
0xf38cf5b3…6049
0x065c9d…c394
2 touches
0 conflicts
0xf6853193…2832
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity