pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,309,113
← previous block
next block →
recent activity
Analyzing
Block #74,309,113
9 transactions · 8 stateful · 2026-05-13 11:13:58 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,309,113
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
0x6a045d6e
#3
0x98717539
#4
updateDataFeedsValuesPartial
#6
0x5339c59f
#7
updateTemporalNumericValuesV1
#8
setData
#5
0x5339c59f
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
0xbbee74c2…567a
0x065c9d…c394
4 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
0x0720e4de…f583
0x065c9d…c394
2 touches
0 conflicts
0x19f32839…8a71
0x065c9d…c394
2 touches
0 conflicts
0x3026ab87…7b11
0x065c9d…c394
2 touches
0 conflicts
0x45ba2282…438d
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
0xbbee74c2e7…6e567a
Audit this contract →
← previous block
·
next block →
recent activity