pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,425,407
← previous block
next block →
recent activity
Analyzing
Block #74,425,407
8 transactions · 6 stateful · 2026-05-14 00:07:46 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,425,407
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
get_block_hash_257335279069929
#4
updateDataFeedsValuesPartial
#5
setData
#7
0x39435dac
#6
0x25e4be58
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0xcb9b0ede…80d8
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0e6ec1e6…3981
0x065c9d…c394
2 touches
0 conflicts
0x3e55f9e3…11d0
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x71bb52bf…f3d7
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x30276c1c08…7247b4
Audit this contract →
← previous block
·
next block →
recent activity