pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,226,288
← previous block
next block →
recent activity
Analyzing
Block #72,226,288
6 transactions · 4 stateful · 2026-05-03 19:45:47 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,226,288
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x9036287a
· blocks 1
#3
updateDataFeedsValuesPartial
#5
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x345667db…c4b7
0x065c9d…c394
4 touches
1 conflict
0x1297b64a…c157
0x065c9d…c394
3 touches
1 conflict
0x43731a09…b18d
0x065c9d…c394
3 touches
1 conflict
0x79358492…f219
0x065c9d…c394
2 touches
0 conflicts
0xbb601fe7…d0d7
0x065c9d…c394
2 touches
0 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x0175b7a6…1db9
0x8d0464…4402
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