pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,432,912
← previous block
next block →
recent activity
Analyzing
Block #74,432,912
6 transactions · 4 stateful · 2026-05-14 00:57:48 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
#74,432,912
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
setData
#2
flash
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f67fe5…8722
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1fa7f952…4600
0x065c9d…c394
2 touches
0 conflicts
0x6553caf8…93c3
0x065c9d…c394
2 touches
0 conflicts
0x69510194…2d61
0x065c9d…c394
2 touches
0 conflicts
0x8974d03e…4f09
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
1 conflict on slot
0x63f67fe5c7…de8722
Audit this contract →
← previous block
·
next block →
recent activity