pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,338,666
← previous block
next block →
recent activity
Analyzing
Block #74,338,666
13 transactions · 9 stateful · 2026-05-13 14:30:33 UTC
Parallelism
69
/100
Blocked
44
%
Avg conflicts / tx
0.54
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,338,666
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#2
execute
#3
0x0756e95c
#5
0xe7be4706
#6
0x98717539
#7
updateDataFeedsValuesPartial
#11
setData
#12
0x39435dac
#4
swapExactIn
#8
0x0c7abd22
· blocks 2
#9
0x0c7abd22
· blocks 1
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
8
w1
9
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74aa6be4…70c3
0xd32edf…ff58
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
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
6 conflicts on slot
0x74aa6be4c7…6a70c3
Audit this contract →
← previous block
·
next block →
recent activity