pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,260,116
← previous block
next block →
recent activity
Analyzing
Block #74,260,116
11 transactions · 10 stateful · 2026-05-13 05:48:00 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,260,116
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x323fe4ce
#5
forward
#6
0x6a041108
#7
setData
#8
0x39435dac
#9
0x39435dac
#10
jMMeC
#2
0x0c7abd22
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
0x98df6446…bb6e
0xd32edf…ff58
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
0x2b0b0af5…a623
0x065c9d…c394
2 touches
0 conflicts
0x4b9b4f1e…6adc
0x065c9d…c394
2 touches
0 conflicts
0x5ffd9d55…d1db
0x065c9d…c394
2 touches
0 conflicts
0x637904e4…339b
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:
0xd32edf66…9fff58
1 conflict on slot
0x98df644694…68bb6e
Audit this contract →
← previous block
·
next block →
recent activity