pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,346,491
← previous block
next block →
recent activity
Analyzing
Block #74,346,491
9 transactions · 9 stateful · 2026-05-13 15:22:35 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,346,491
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0x1ffa3c9b
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
updatePriceFeedsIfNecessary
#7
0x6a0497b2
#8
setData
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0xebd4e235…6945
0x8d66a4…3095
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x010934db…c694
0x065c9d…c394
2 touches
0 conflicts
0x29840a3c…1c9a
0x065c9d…c394
2 touches
0 conflicts
0x3ebe5971…ac35
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
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:
0x8d66a43f…113095
1 conflict on slot
0x8a35acfbc1…6bd1aa
Audit this contract →
← previous block
·
next block →
recent activity