pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,505,980
← previous block
next block →
recent activity
Analyzing
Block #74,505,980
11 transactions · 8 stateful · 2026-05-14 09:04:23 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,505,980
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
updateDataFeedsValuesPartial
#4
batch
#5
0x6df9e92b
· blocks 1
#7
0x6a05908f
#8
setData
#9
0x925076…48d7
#10
0x39435dac
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…0003
0x240fca…48b4
2 touches
0 conflicts
0x00000000…0005
0x240fca…48b4
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:
0x23c26bd5…547777
1 conflict on slot
0x81a7ba4dd6…568c4b
Audit this contract →
← previous block
·
next block →
recent activity