pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,098,243
← previous block
next block →
recent activity
Analyzing
Block #72,098,243
6 transactions · 5 stateful · 2026-05-03 05:29:45 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,098,243
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67a7528c
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5614236e…5ae3
0x065c9d…c394
2 touches
0 conflicts
0xaff6435a…fa04
0x065c9d…c394
2 touches
0 conflicts
0xcc3ab048…f541
0x065c9d…c394
2 touches
0 conflicts
0xd629d1fb…7f49
0x065c9d…c394
2 touches
0 conflicts
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity