pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,228,833
← previous block
next block →
recent activity
Analyzing
Block #72,228,833
5 transactions · 4 stateful · 2026-05-03 20:02:54 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,228,833
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82adad32…3f76
0x065c9d…c394
4 touches
1 conflict
0xd607f070…4f75
0x065c9d…c394
4 touches
1 conflict
0xfd0aafcc…9918
0x065c9d…c394
4 touches
1 conflict
0x6e19ba42…2586
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x599b3b89…e58a
0x065c9d…c394
3 touches
1 conflict
0xd4d1698d…fe6d
0x065c9d…c394
3 touches
1 conflict
0xbf04f37d…85f2
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
1 conflict on slot
0x82adad3278…7b3f76
Audit this contract →
← previous block
·
next block →
recent activity