pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,860,366
← previous block
next block →
recent activity
Analyzing
Block #72,860,366
8 transactions · 8 stateful · 2026-05-06 18:15:11 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,860,366
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x121eab2f
· blocks 3
#6
0xeffdedb0
#7
setData
#3
0xed82b078
· blocks 2
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x8de1ff77…a342
0x065c9d…c394
3 touches
1 conflict
0x82e38dc7…4574
0x065c9d…c394
2 touches
0 conflicts
0x94cd9659…661b
0x065c9d…c394
2 touches
0 conflicts
0xff165e6d…4a23
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
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