pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,731,055
← previous block
next block →
recent activity
Analyzing
Block #74,731,055
13 transactions · 10 stateful · 2026-05-15 10:11:40 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,731,055
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
· blocks 1
#3
0xed82b078
#4
0x98717539
#5
0x98717539
#6
nothingToSeeHere_04ikDO9
#7
claimRewards
#8
0x6df9e92b
· blocks 1
#10
updateDataFeedsValuesPartial
#11
setData
#12
exactInputSingle
#2
execute
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xb72e62…7777
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
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:
0xee8c0e9f…481242
1 conflict on slot
0x56a919c43e…27ab49
Audit this contract →
← previous block
·
next block →
recent activity