pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,308,994
← previous block
next block →
recent activity
Analyzing
Block #74,308,994
9 transactions · 9 stateful · 2026-05-13 11:13:11 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,308,994
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xccf50a51
#2
collect
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a045d3f
#8
setData
#3
0x6df9e92b
· blocks 1
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0x00000000…0001
0x776059…1d8d
4 touches
1 conflict
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
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:
0x3bd359c1…15433a
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity